pp108 : Configuring Apache TomEE

Configuring Apache TomEE
The topics describes the actions you must perform to configure Apache TomEE for Process Platform.

Executing configureapplicationserver script

Before you begin, ensure that the Process Platform Web pages are available to TomEE and that you load the Servlet filters. The <Process Platform installation directory>/bin folder contains the configureapplicationserver.sh file for Linux, and the configureapplicationserver.ps1 file for Windows. When you install the configureapplicationserver script, it performs the following actions:

  1. Provides folder permissions for Process Platform to deploy WAR files and allows TomEE to read and write in specific folders of the Process Platform installation directory.
  2. Adds Process Platform jars to the classpath of TomEE.
  3. Add configuration to the TomEE daemon (Linux) or service (Windows).
  4. Add context files to expose web pages and services in TomEE.

When uninstalling Process Platform, these actions are reverted and the deployed Web application Entity Runtime is removed.

When you select the Automatic Deployment option in the TomEE Details page of the Process Platform installer, the installer and uninstaller executes the configureapplicationserver script. If you do not select this option, the administrator can review the changes that are made to the Application Server. After reviewing, you must execute the configureapplicationserver script manually.

In a Linux terminal, execute the following as root:

cd <Process Platform installation directory>/bin
./configureapplicationserver.sh install

In Windows, in a PowerShell prompt, execute the following as an administrator:

cd <Process Platform installation directory>\bin
Set-ExecutionPolicy Bypass -Scope Process
.\configureapplicationserver.ps1 install

To uninstall, execute the same scripts by replacing the install argument  with uninstall.

Content expiration

When installing the Process Platform, the Advanced Web server configuration panel enables configuring content expiration. These settings do not apply when using TomEE as a Web server.
To configure content expiration for TomEE, use the property com.cordys.web.caching.maxage in wcp.properties. This property takes an integer value, followed by "s", "m", "h", or "d", indicating a value in seconds, minutes, hours or days. See the following examples:

Property value Caching header
10s Cache-Control:max-age=10
15m Cache-Control:max-age=900
1h Cache-Control:max-age=3600
30d Cache-Control:max-age=2592000
<property not set> Cache-Control:no-cache

After changing this setting, restart TomEE and Process Platform.

Other configuration items

See also: